Subject: RFC1593 - SNA APPN Node MIB

From: [email-masked]
Date: Thu, 10 Mar 94 13:58:55 EST

To SNMP MIBers:

In case you have not got this, the APPNMIB implemented in IBM's
APPN OEM code package has become an informational RFC, RFC1593.
Now for vendors who licensed IBM's APPN code, you have an RFC
number to use when referencing the APPN MIB.

Get the RFC through anonymous FTP to any IETF ftp server,
or from ibmstandards.cary.ibm.com (under aiw/snasnmp directory).

The original IETF announcement is attached for your reference.
Any questions, comments?  Please send to this mailing list!

Robin Cheng,  [email-masked]
Mike Allen, [email-masked]
- - - - - - - - - - - -- - - - - - - - - - - -  - - - - - - -- -  - -
To: IETF-Announce: ;
Subject: RFC1593 on SNA APPN Node MIB
Cc: [email-masked]
Date: Thu, 10 Mar 94 07:23:29 PST
Sender:[email-masked]
From: "Joyce K. Reynolds" <[email-masked]>

--NextPart

A new Request for Comments is now available in online RFC libraries.

        RFC 1593:

        Title:      SNA APPN Node MIB
        Author:     W. McKenzie & J. Cheng
        Mailbox:    [email-masked],
                    [email-masked]
        Pages:      120
        Characters: 207,882
        Updates/Obsoletes:  none

This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer
Networking (APPN) nodes.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email-masked].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email-masked] with the message body
help: ways_to_get_rfcs.  For example:

        To: [email-masked]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email-masked].  Please consult RFC 1543, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[email-masked]"

Content-Type: text/plain
Content-ID: <[email-masked]>

SEND /rfc/rfc1593.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1593.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <[email-masked]>

--OtherAccess--
--NextPart--

---

From: [email-masked]
Date: Thu, 31 Mar 94 15:56:46 EST

I would like to summarize the result from the polling
regarding RFC1593 - SNA APPN Node MIB.

We have collected responses from the following vendors (as of 3/31/94)
Every vendor on this list showed some degree of interest in RFC1593.
Some are interested and reviewing the MIB,
some will support it in their products,
some even suggested areas where the MIB can be improved.
It is clear that AIW should keep investing on APPN MIB support.
- - - - - -
Systems Strategies/Apertus
Digital Technology, Burlington, Mass
Metaplex
Tandem Computers
Cabletron Systems
cisco Systems, Inc.
3Com
Northern Telecom Magellan Networks
Data Connection Limited
Wellfleet
IBM
- - - - - -
Your ideas or suggestions in this area are appreciated!

Robin Cheng, IBM Networking Systems
phone: (919)254-4434
[email-masked]